|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 26.2
|
|
Title:
|
External Network Network Interfaces (ENNI) and Operator Service Attributes
The Metro Ethernet Network Architecture Framework - Part 1: Generic Framework (MEF 4) specifies a reference point that is the interface between two Carrier Ethernet Networks (CENs), where each Operator CEN is under the control of a distinct administrative authority. This reference point is termed the External Network Network Interface or ENNI. The ENNI is intended to support the extension of Ethernet services across multiple Operator CENs.
|
|
|
2.
|
Status of approval:
|
|
|
Approved in August 2016
|
|
3.
|
Justification for the specific reference:
|
|
|
The Ethernet ENNI definitions in MEF 26.2 supplement MEF 10.3 to form the basis of this Recommendation.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
No known issues.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Commonly referenced all over the world for metro Ethernet services.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Commonly referenced all over the world for metro Ethernet services.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
MEF 26.2 is part of a set of MEF Techcnical Specifications branded as "Carrier Etherent 2.0"
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] IEEE Std 802.1AX – 2008, IEEE Standard for Local and metropolitan area networks – Link Aggregation, November 2008./
[2] IEEE Std 802.1AX – 2014, IEEE Standard for Local and metropolitan area networks – Link Aggregation, December 2014./
[3] IEEE Std 802.1Q – 2014, IEEE Standard for Local and metropolitan area networks--Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks, 3 November 2014./
[4] IEEE Std 802.3 – 2012, IEEE Standard for Ethernet, 30 August 2012./
[5] International Telecommunication Union, Recommendation Y.1563, Global information infrastructure, internet protocol aspects and next-generation networks, Internet protocol aspects – Quality of service and network performance, Ethernet frame transfer and availability performance, 2009./
[6] Internet Engineering Task Force RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, March 1997./
[7] Internet Engineering Task Force RFC 2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers, December 1998./
[8] Internet Engineering Task Force RFC 2579. Textual Conventions for SMIv2, April 1999. /
[9] Internet Engineering Task Force RFC 3393, IP Packet Delay Variation Metric for IP Performance Metric (IPPM), November 2002./
[10] MEF Forum, MEF 4, Metro Ethernet Network Architecture Framework – Part 1: Generic Framework, May 2004./
[11] MEF Forum, MEF 6.2, Ethernet Services Definitions - Phase 3, July 2014./
[12] MEF Forum, MEF 10.3, Ethernet Services Attributes Phase 3, October 2013./
[13] MEF Forum, MEF 10.3.2, Amendment to MEF 10.3 - UNI Resiliency Enhancement, November 2015./
[14] MEF Forum, MEF 11, User Network Interface (UNI) Requirements and Framework, November 2004./
[15] MEF Forum, MEF 16, Ethernet Local Management Interface (E-LMI), January 2006./
[16] MEF Forum, MEF 17, Service OAM Requirements & Framework – Phase 1, April 2007./
[17] MEF Forum, MEF 23.2, Carrier Ethernet Class of Service – Phase 3, ????./
[18] MEF Forum, MEF 26.1, External Network Network Interface (ENNI) – Phase 2, January 2012./
[19] MEF Forum, MEF 28, External Network Network Interface (ENNI) Support for UNI Tunnel Access and Virtual UNI, October 2010./
[20] MEF Forum, MEF 30.1, Service OAM Fault Management Implementation Agreement: Phase 2, April 2013./
[21] MEF Forum, MEF 33, Ethernet Access Services Definition, January 2012. /
[22] MEF Forum, MEF 35.1, Service OAM Performance Monitoring Implementation Agreement, May 2015./
[23] MEF Forum, MEF 41, Generic Token Bucket Algorithm, October 2013./
[24] MEF Forum, MEF 45, Multi-CEN L2CP, July 2014./
[25] MEF Forum, MEF 51, OVC Services Definitions, July 2015.
|
|
9.
|
Qualification of
MEF:
|
|
|
The MEF was recognized under the provisions of ITU-T Recommendation A.5 on 24 September 2002. Qualifying information is on file with TSB.
9.5 The IPR policy of the MEF may be found in Article 10 of the MEF Bylaws which are available on the MEF public WEB site metroethernetforum.org.
9.6 All MEF Technical Specifications, Implementation Agreements, and Test Specifications are approved by an electronic letter ballot of all MEF members. For a MEF document to pass an electronic letter ballot at least a quorum of members (defined by the MEF bylaws as 1/3 of the MEF membership) must vote Yes or No. In addition, of the Yes plus No votes at least 75% of the votes must be Yes.
9.7 All published MEF documents are available for download free of charge in PDF or WORD format from the MEF public WEB site www.metroethernetforum.org .
9.8 Each revision of a given MEF document has a different MEF number.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
